Skip to main content
Feedback

Installing the initial runtime cluster node on Linux

Install the downloaded Linux version of the initial runtime cluster by running the executable file.

Before you begin

Runtime clusters require the Java 8 JRE or the Java 11 JDK. Boomi recommends Java 11. Boomi internally tested Amazon Corretto OpenJDK Java 1.8.0_382 and Amazon Corretto Open JDK 11.0.20.8.1.

Before completing these steps, download the runtime cluster installer and set up Linux shared directories. The installer gives you an option to select local directories for storing working data and temporary data. Boomi strongly recommends that you select the Use Local Storage for Runtime Assets setting. If you select local directories, ensure that these directories exist before you run the installer. The installer does not create the directories for you. For new runtimes, you can enable local storage during installation.

The installer installs a private copy of Java 11 (11.0.20.8.1) for the runtime cluster to use. Alternatively, you can manage your own distribution of the Java 11 JDK by downloading the JDK from Amazon prior to installing the runtime cluster.

note

If you manage your own Java version instead of using the distribution provided by Boomi, runtime clusters using forked execution require the Java 8 JDK rather than the JRE. Java 11 is distributed as a JDK by default, so no additional considerations are required when using this version.

note

If you choose not to use the user interface to install the initial runtime cluster node, use the console mode option (-c) of the install4j installer.

Procedure

  1. Locate the runtime cluster installer file that you saved to your machine.

    After downloading the file, you can run the installation wizard from a command line, which Boomi recommends, or from the user interface.

  2. Do one of the following:

    • If you want to run the installer in console mode from a command line, run the file with the -c flag:

      sh /<path>/molecule_install64.sh -c

    • If you install with the user interface, double-click the install file (you might need to change the properties to allow the file to run: chmod +x molecule_install64.sh) or run the file from the command line without the command-only flag:

      sh /<path>/molecule_install64.sh

  3. If the installer cannot find the JRE on your machine, you receive a download prompt.

  4. On the Welcome page, click Next.

  5. On the User Information page:

    1. Select User Name and Password or Token, depending on how you want to authenticate the runtime cluster.

    2. Enter one of the following, depending on the selected option:

      • Your user name and password

      • A valid installer token

      You can generate installer tokens when you download the runtime cluster installer from the Cluster Setup dialog. When generating tokens, they are valid only for the specific account and runtime clouds. Tokens expire after a set amount of time ranging from 30 minutes to 24 hours.

    3. Enter a name for the runtime cluster.

      The name is what you see when you go to Manage > Runtime Management. The name defaults to the local host name, and you can change it to something more familiar.

      note

      The following characters are reserved and cannot be used in the name: asterisk (*), backslash (\), caret (^), colon (:), dollar sign ($), greater than (>), less than (<), percent (%), pipe (|), question mark (?), quotation mark ("), slash mark (/), Yen sign (¥).

    4. Click Next.

    You connect to the Boomi Enterprise Platform and the platform authenticates your credentials.

    If you specified a user name and password, the Accounts page appears.

    If you specified an installer token, the Select Directory for Symlinks page appears and you can skip to step 7.

  6. (Optional) On the Accounts page:

    1. You see a list of accounts if your user name has access to multiple accounts. Next, select the account to which this is associated. This step typically applies only to partners.

      In the command line, each account name is followed by a number within square brackets, for example, [123]. To select an account, enter its number.

    2. Click Next.

  7. (Optional) On the Environment page:

    1. (Optional) If you created environments already, a list appears. Select the one to which this runtime cluster is attached. If you do not select one, your new runtime cluster appears in the list of Unattached Runtimes on the Runtime Management page.

    2. Click Next.

  8. On the Select Destination Directory page, select the folder where you installed the runtime cloud cluster and click Next.

  9. On the Select Local Cluster Node Directories page:

    1. Select a local directory for storing the runtime cluster node.

      The "Yes, store assets locally" is selected by default and strongly recommended. You must provide a local directory path with this option. If you select "No, use cluster shared storage instead (not recommended)" you will be directed to a new dialog box to create a symliks and provide a destination directory.

    2. Select a directory for storing the runtime cluster node’s temporary data. This value sets the -Djava.io.tmpdir property in the <runtime_install_directory>/bin/atom.vmoptions file.

    3. Click Next.

  10. On the Select Directory for Symlinks page, select the Don't create symlinks check box and click Next.

  11. On the Information page, review the installation settings, and click Next.

  12. When the installation is complete, click Finish to start the runtime cluster.

Results

The runtime cluster runs as a daemon thread. You can view the runtime cluster online by going to Manage > Runtime Management.

The installation log file is located in <molecule_installation_directory>/tmp and its file name starts with i4j.

Next steps

Next, you can install additional nodes.

On this Page